home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Performance Co-Pilot 1.3
/
SGI Performance Co-Pilot 1.3.iso
/
dist
/
pcp.idb
/
usr
/
share
/
catman
/
u_man
/
cat1
/
pmnscomp.z
/
pmnscomp
Wrap
Text File
|
1997-04-03
|
6KB
|
133 lines
PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111)))) PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111))))
NNNNAAAAMMMMEEEE
ppppmmmmnnnnssssccccoooommmmpppp - compile an ASCII performance metrics namespace into binary
format.
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
ppppmmmmnnnnssssccccoooommmmpppp [----dddd] [----ffff] [----nnnn _n_a_m_e_s_p_a_c_e] _o_u_t_f_i_l_e
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
ppppmmmmnnnnssssccccoooommmmpppp compiles a Performance Metrics Name Space (PMNS) in ASCII format
into a more efficient binary representation. ppppmmmmLLLLooooaaaaddddNNNNaaaammmmeeeeSSSSppppaaaacccceeee(3) is able
to load this binary representation significantly faster than the
equivalent ASCII representation.
If _o_u_t_f_i_l_e already exists ppppmmmmnnnnssssccccoooommmmpppp will exit without overwriting it.
By convention, the name of the compiled namespace is that of the root
file of the ASCII namespace, with ....bbbbiiiinnnn appended. For example, the root
of the default PMNS is a file named rrrrooooooootttt and the compiled version of the
entire namespace is rrrrooooooootttt....bbbbiiiinnnn.
The options are;
----dddd By default the PMNS to be compiled is expected to contain at most
one name for each unique Performance Metric Id (PMID). The ----dddd
option relaxes this restriction and allows the compilation of a PMNS
in which multiple names may be associated with a single PMID.
Duplicate names are useful when a particular metric may be logically
associated with more than one group of related metrics, or when it
is desired to create abbreviated aliases to name a set of frequently
used metrics.
----ffff Force overwriting of an existing _o_u_t_f_i_l_e if it already exists.
----nnnn Normally ppppmmmmnnnnssssccccoooommmmpppp operates on the default PMNS, however if the ----nnnn
option is specified an alternative namespace is loaded from the file
_n_a_m_e_s_p_a_c_e.
The default input PMNS is found in the file /_v_a_r/_p_c_p/_p_m_n_s/_r_o_o_t unless the
environment variable PPPPMMMMNNNNSSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTT is set, in which case the value is
assumed to be the pathname to the file containing the default input PMNS.
FFFFIIIILLLLEEEESSSS
/_v_a_r/_p_c_p/_p_m_n_s/* default PMNS specification files
/_v_a_r/_p_c_p/_p_m_n_s/_r_o_o_t._b_i_n compiled version of the default PMNS, when then
environment variable PPPPMMMMNNNNSSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTT is unset
/_v_a_r/_p_c_p/_p_m_n_s/_s_t_d_p_m_i_d some standard macros for PMID generation
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ppppmmmmnnnnssssaaaadddddddd(1), ppppmmmmnnnnssssddddeeeellll(1), ppppmmmmnnnnssssmmmmeeeerrrrggggeeee(1), PPPPMMMMAAAAPPPPIIII(3), ppppmmmmLLLLooooaaaaddddNNNNaaaammmmeeeeSSSSppppaaaacccceeee(3),
ppppmmmmTTTTrrrriiiimmmmNNNNaaaammmmeeeeSSSSppppaaaacccceeee(3) and ppppmmmmnnnnssss(4).
PPPPaaaaggggeeee 1111
PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111)))) PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111))))
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
Cannot open ``xyz'' - the filename for the root of the PMNS that was
passed to ppppmmmmLLLLooooaaaaddddNNNNaaaammmmeeeeSSSSppppaaaacccceeee(3) is bogus
Illegal PMID - either one of the three PMID components (see ppppmmmmnnnnssss(4)) is
not an integer, or the value for one of the components is negative, or
too large.
Expected ... - specific syntax errors when a particular type of lexical
symbol was expected and not found; the messages are intended to be self-
explanatory.
Internal botch - implementation problem for the parser ...
Duplicate name ``abc'' in subtree for ``pqr.xyz'' - for each non-leaf
node, the names of all immediate descendents must be unique.
No name space entry for ``root'' - the special non-leaf node with a
pathname of ``root'' defines the root of the PMNS, and must appear
somewhere in the PMNS specification.
Multiple name space entries for ``root'' - more than one ``root'' node
does not make sense!
Disconnected subtree (``abc.xyz.def'') in name space - the pathname for
this non-leaf node does not correspond to any pathname in the PMNS, hence
this non-leaf node is ``orphaned'' in the PMNS.
Cannot find definition for non-terminal node ``xyz'' in name space - a
non-terminal node is named as part of its parent's specification, but is
never defined.
Duplicate metric id (xxx) in name space for metrics ``abc'' and ``xyz'' -
each PMID must be unique across the PMNS.
PPPPaaaaggggeeee 2222